home *** CD-ROM | disk | FTP | other *** search
- Subject: FW_CODPart::ClonePartInfo
- Sent: 7/21/96 5:45 AM
- Received: 7/22/96 10:48 AM
- From: Hutchings, Richard B. "Brad", brad@hutchings-software.com
- Reply-To: ODF Interest, ODF-Interest@CILabs.ORG
- To: OpenDoc Development Framework Discussion List, ODF-Interest@CILabs.
-
- What is the future plan for FW_CODPart::ClonePartInfo? Right now, it calls
- WritePartInfo, which calls FW_CFrame::WritePartInfo. There is code
- commented out to call FW_CFrame::ClonePartInfo.
-
- The reason I ask is that I'm caching a little bit of data with each frame.
- The data can take awhile (2-3 seconds per frame) to generate from scratch,
- so I use a "just in time" strategy to compute parts of it. However, to
- improve execution speed on reopening of my part, I bite the bullet and
- compute everything that isn't already cached during the
- FW_CFrame::ExternalizeFrame.
-
- So, the big problem is that inside FW_CFrame::ExternalizeFrame, there's no
- easy way of telling whether it's writing the part info, or cloning it. If I
- knew it were cloning, I wouldn't bother recomputing all that garbage. Then,
- copies and drags would happen much quicker.
-
- I'd just like to know the direction that ODF is going, so that as I modify
- the framework this time (ugh!), I'll minimize my maintenance problems...
-
- Thanks,
-
- Brad
-
- <mailto: "Brad Hutchings" brad@hutchings-software.com>
- <http://www.hutchings-software.com>
-
- Ask me about:
- Hutchings Software's Rapid-I(tm) Button
- Hutchings Software's Essential Strips(tm)
-
-
-